updated RELEASE.md for the 2020.02 release (issue #25) #27
Conversation
RELEASE.md
Outdated
| ***drivers/*** | ||
| - renamed ***fvGFS*** to ***SHiELD*** | ||
| - renamed ***coupled*** to ***GFDL*** |
There was a problem hiding this comment.
This happened at the beginning of the dev/gfdl branch. It's not new to this release.
There was a problem hiding this comment.
@thomas-robinson I was thinking of those coming from the locked internal project and starting to use the publicly available repository. Do you have suggested wording for that?
There was a problem hiding this comment.
- coupled is GFDL (for internal GFDL users) (?) I'm not sure. This is probably something that the liaison's should convey to the groups
RELEASE.md
Outdated
| atmosphere.F90: 'mytile' is renamed 'mygrid' | ||
| ***model_nh_null/*** | ||
| - has been removed | ||
| - non-hydrostatic capability is now included as a runtime configurable option |
There was a problem hiding this comment.
Is this simple to do? If so, could there be instructions?
There was a problem hiding this comment.
@thomas-robinson While I can technically provide namelist options, it may require extra help on the science side. I believe one should start by reading all available documentation in the technical memorandum and on the GFDL website for FV3. What do you think?
There was a problem hiding this comment.
I think if it's more complicated than something like do_nh = .true. then it's not worth mentioning here. I was just wondering if it was really that simple (which I didn't think it was)
…DL#27) * add fh00 post control file, add restart output at specified forecast hours, ugwd bug fixes * fv3atm NOAA-GFDL#15:Add support for GEFS-Aerosols restart capability * remove comment prints * fix RunDuration in atmos fcst side * update post_gfs with new post changes * comment out print line * point fv3 dycore to the latest NOAA-EMC dev/emc branch
CMake Fixes to support JEDI
Updates the release notes for the GFDL branch 2020.02 release
Fixes #25